Skip to main content

Client ID

The clientId is a required parameter on every request to the Feed Clips API. It identifies a single end user of your application and is used to define a MAU for billing purposes.

What It Is​

The clientId is an opaque, non-guessable identifier that you generate and manage. Feed does not authenticate users — it trusts your application to supply a consistent, unique identifier per user. The value itself is treated as an opaque string; Feed does not interpret its format.

Requirements​

  • Required on all requests. Every API call must include a clientId.
  • Stable across platforms and sessions. The same user on iOS, Android, and Web should send the same clientId.
  • No PII. The value must not contain personally identifiable information such as an email address, username, or phone number.
  • At least 8 characters long.

Why Stability Matters​

A drifting or inconsistent clientId creates cascading problems:

  • Analytics. Engagement metrics (plays, adds, shares) are attributed per user over time. An inconsistent clientId introduces inaccuracies.
  • Billing. Usage is attributed to your account at the per-user level based on unique clientId values. Inconsistent IDs introduce the risk counting the same user as multiple MAUs.

Examples​

Same user, multiple devices. A user signs in on their phone and selects a clip. Later they open your app on a tablet and add the same clip to a video. Both devices should send the same clientId so all activity appears under a single user.

Same user, multiple sessions. A user previews music today and returns next week to publish content. Both sessions should send the same clientId so Feed sees a single, continuous engagement history.

Anonymous guest user upgrading to an account. A guest user tries the app, then creates an account. Migrate the guest clientId to the account's persistent clientId to preserve history rather than starting fresh.

Implementation Tips​

  • Generate a UUID v4 for each real user identity in your system and persist it server-side.
  • Reuse that UUID across platforms (mobile, web) when the user is authenticated and recognized.
  • For anonymous users, create a temporary clientId and promote it to the account's permanent ID when they sign in, so the session history carries over.
  • Never derive the clientId from device identifiers alone. Device resets or transfers would silently change the identifier.